Message ordering for network based mobility management systems

ABSTRACT

The claimed subject matter relates to systems and methods for processing messages in a wireless communications environment. In an aspect, a communications method is provided. The method includes initiating a registration with a network domain node and generating sequence information with respect to the registration. The sequence information is then employed to facilitate further communications with the network domain node.

CLAIMS OF PRIORITY

The present Application for Patent is a continuation of U.S. patentapplication Ser. No. 15/931,004, entitled “MESSAGE ORDERING FOR NETWORKBASED MOBILITY MANAGEMENT SYSTEMS,” filed May 13, 2020, which is acontinuation application of U.S. patent application Ser. No. 15/182,247,entitled “MESSAGE ORDERING FOR NETWORK BASED MOBILITY MANAGEMENTSYSTEMS,” filed Jun. 14, 2016, which is a divisional application of U.S.patent application Ser. No. 11/968,576, issued as U.S. Pat. No.9,392,434, entitled “MESSAGE ORDERING FOR NETWORK BASED MOBILITYMANAGEMENT SYSTEMS,” filed Jan. 2, 2008, which claims the benefit ofU.S. Provisional Application No. 60/885,983, entitled “A METHOD ANDAPPARATUS FOR MOBILITY MANAGEMENT MESSAGE ORDERING,” filed Jan. 22,2007, each of which is incorporated herein by reference in its entirety.

BACKGROUND Field

The following description relates generally to communications systems,and more particularly to ordering of registration messages to accesspoints that are in a communication with a mobile device.

Background

Communication networks, such as wireless communication networks,broadband networks, and other suitable networks are utilized inconnection with transferring data, wherein data can include wordprocessing files, streaming video, multimedia files, voice data, and/orthe like. Such networks are often employed with protocols such asInternet Protocol (IP) for transferring data in accordance with a publicnetwork such as the Internet. An extension of IP protocols relates tomobile devices and is known as Mobile Internet Protocol (MIP). Anothervariant is Proxy Mobile Internet Protocol (PMIP). Such mobile protocolsare often employed with a network domain that includes nodes such asaccess nodes and Local Mobility Anchors (LMA) for example that oftenemploy the mobile IP protocols in conjunction with a domain protocol tomanage the respective devices within the domain.

One such domain protocol is referred to as a Network-based LocalizedMobility Management (NETLMM) protocol. In contrast to MIP protocol whichis considered a global mobility management protocol to control IP linksas communications devices change location, NETLMM and PMIP help localizethe management of topologically small device movements. Limiting thereach of the respective protocol responsibilities is more preferable tohandle local movements since protocol complexities are reduced.Generally, NETLMM provides for efficient support for mobile nodescommunicating with peers both outside and inside the same mobilitydomain when mobile nodes move across different access routers (or nodes,or points). These movements typically require no extra host stacksupport or complex security and signaling interactions between mobilenode and the respective access network. By utilizing the neighbor accessrouter information in the domain, NETLMM can achieve very fast andsmooth handover performance to suit the requirements of most real-timeand interactive multimedia applications.

Network based mobility management systems employing technologies such asNETLMM, PMIP are generally considered mobility management systems thatdo not require mobility management signaling from a mobile device tooperate. Instead, the network or domain changes message routing withinthe network based on link layer or other triggers. A well understoodlimitation of such mechanisms is that they can only operate with mobilesthat maintain a single link to the network. In other words the mobilitymanagement system points to a single point of attachment for eachmobile. Since the mobile is assumed to have only one link with an NETLMMdomain for example, at any one time the NETLMM protocol must ensure thatthe local mobility anchor (LMA) redirects the mobile device's traffic tothe correct access router i.e., the access router the mobile isconnected to. To perform this operation, access routers sendregistration messages to the LMA when a mobile device creates a linkwith the LMA. Assuming the mobile device can only have one link at thetime, the order in which the registration messages reach the LMA isassumed to be the same as the order in which the mobile device createslinks with different access routers. This assumption can hold if themovement between access routers is not very frequent. More specifically,the assumption holds when the time between link creations is larger thanthe time it takes for the access router to register with the LMA.

Referring to prior art FIG. 10, an example domain 1000 is illustrated.The domain 1000 includes an LMA 1010 that communicates with access nodes(AN) (or routers) 1020 and 1030. The AN's 1020,1030 communicate withaccess point (AP) groups 1040 and 1050 respectively, where such groupsmay service a mobile device 1060. The mobile device 1060 maintains alink with Access Point 2 (AP2) 1070, which is directly connected to theAN at 1020. In this example, NETLMM protocol schemes work relativelywell since only movement between ANs 1020 and 1030 is triggering NETLMMdevice registrations, while movement between APs at 1040 or 1050 underthe same AN 1020 or 1030 do not trigger such registrations. Even in thiscase, however, movement between AP2 at 1070 and AP4 at 1080 can causeout of order delivery of the registrations to the LMA 1010, if forexample the mobile device moves too fast or if it moves back and forthbetween AP2 1070 and AP4 1080, a condition commonly referred to as“ping-pong.” As can be appreciated, back and forth movements can causecommunications problems within the domain 1000.

SUMMARY

The following presents a simplified summary in order to provide a basicunderstanding of some aspects of the claimed subject matter. Thissummary is not an extensive overview, and is not intended to identifykey/critical elements or to delineate the scope of the claimed subjectmatter. Its sole purpose is to present some concepts in a simplifiedform as a prelude to the more detailed description that is presentedlater.

Message ordering principles are applied to network-based mobilitymanagement systems and protocols to facilitate orderly communicationswithin a network or domain. During registration of a communicationchannel between a mobile device and a node in the domain such as a LocalMobility Anchor (LMA) for example, sequential information can be appliedto the registration to facilitate ordering of messages in the domain andwith respect to the mobile device. Sequential information can take theform of a sequence number or timestamp information for example that canbe assigned by the device or proxy node within the domain. When aninitial communication commences with the LMA, the sequence number can beassigned to a registration occurring between the LMA and the mobiledevice. Upon movement of a device where other access nodes or accesspoints become involved, a subsequent registration can occur with theLMA. During the subsequent registration, the previous sequence numbercan be incremented and employed for the subsequent registration. The LMAor other controlling node then employs the sequence number to trackwhere messages should be routed across the domain and in view of therespective sequence number received. In this manner, out of orderdelivery problems associated with prior systems and protocols ismitigated.

To the accomplishment of the foregoing and related ends, certainillustrative aspects are described herein in connection with thefollowing description and the annexed drawings. These aspects areindicative, however, of but a few of the various ways in which theprinciples of the claimed subject matter may be employed and the claimedsubject matter is intended to include all such aspects and theirequivalents. Other advantages and novel features may become apparentfrom the following detailed description when considered in conjunctionwith the drawings.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a high level block diagram of a system that is provided toillustrate message ordering in a communications environment.

FIG. 2 is a block diagram of an example network access system that canemploy sequence data to form communications links and facilitate messageordering.

FIG. 3 is a message flow diagram that illustrates example messages andregistrations depicted in FIG. 2.

FIG. 4 illustrates an example proxy-based system.

FIG. 5 is a message flow diagram that illustrates example messages andregistrations depicted in FIG. 4.

FIG. 6 illustrates an example sequence process for ordering messages.

FIGS. 7 and 8 illustrate example logical modules for processing sequencemessages and registrations.

FIG. 9 illustrates an example communications apparatus that employssequential data to form communications links.

FIG. 10 illustrates a prior art network based mobility managementsystem.

FIG. 11 illustrates an example communications system.

FIG. 12 illustrates an example end node.

FIG. 13 illustrates an example access node.

FIG. 14 illustrates an example end node communicating with an exampleaccess node.

DETAILED DESCRIPTION

Systems and methods are provided to facilitate message ordering innetwork-based mobility management systems. In an aspect, acommunications method is provided. The method includes initiating aregistration with a network domain node and generating sequenceinformation with respect to the registration. The sequence informationis then employed to facilitate further communications with the networkdomain node. The network domain node can be a Local Mobility Anchor forexample, operating with such example protocols as proxy mobile InternetProtocol and Network-based localized mobility management protocol.

Furthermore, various aspects are described herein in connection with aterminal. A terminal can also be called a system, a user device, asubscriber unit, subscriber station, mobile station, mobile device,remote station, remote terminal, access terminal, user terminal, useragent, or user equipment. A user device can be a cellular telephone, acordless telephone, a Session Initiation Protocol (SIP) phone, awireless local loop (WLL) station, a PDA, a handheld device havingwireless connection capability, a module within a terminal, a card thatcan be attached to or integrated within a host device (e.g., a PCMCIAcard) or other processing device connected to a wireless modem.

Moreover, aspects of the claimed subject matter may be implemented as amethod, apparatus, or article of manufacture using standard programmingand/or engineering techniques to produce software, firmware, hardware,or any combination thereof to control a computer or computing componentsto implement various aspects of the claimed subject matter. The term“article of manufacture” as used herein is intended to encompass acomputer program accessible from any computer-readable device, carrier,or media. For example, computer readable media can include but are notlimited to magnetic storage devices (e.g., hard disk, floppy disk,magnetic strips . . . ), optical disks (e.g., compact disk (CD), digitalversatile disk (DVD) . . . ), smart cards, and flash memory devices(e.g., card, stick, key drive . . . ). Additionally it should beappreciated that a carrier wave can be employed to carrycomputer-readable electronic data such as those used in transmitting andreceiving voice mail or in accessing a network such as a cellularnetwork. Of course, those skilled in the art will recognize manymodifications may be made to this configuration without departing fromthe scope or spirit of what is described herein.

Referring now to FIG. 1, a system 100 illustrates message orderingprinciples in a communications environment. A network or domain 110includes at least one domain node 120 that communicates to one or moreaccess components 130, where the access components can include interfacepoints to the domain such as access nodes, access routers, basestations, and so forth. A mobile device 140 attempts to establishcommunications with the domain node 120 via the access components 130.For instance, the mobile device 140 may attempt to form a firstcommunications link via a first access component at 130 and after movingto another location, the mobile device forms a subsequent link such asthrough a second access component at 130. As can be appreciated, aplurality of such communications links can be formed between the mobiledevice 140, access components 130, and the domain node 120. Asillustrated, for the respective communications links formed between themobile device 140 and the access components 130, a packet of sequencedata 150 (per communications link) is generated by the device 140 whenan initial communications link is formed. As shown, a proxy node 160 canbe employed to cause switchovers between access components 130 based offof signal quality determinations for example and can also be employed tofacilitate generation of the sequence data 150 as will be described inmore detail below.

In general, the sequence data 150 can be employed for message orderingin a network-based mobility management system to facilitate orderlycommunications within the domain 110. During registration of acommunication channel between the mobile device 140 and the domain node120 in the domain 110 such as a Local Mobility Anchor (LMA) for example,sequential information or data 150 can be applied to the registration tofacilitate ordering of messages in the domain 110 and with respect tothe mobile device 140. Sequential data 150 can take the form of asequence number or timestamp information for example that can beassigned by the device 140 or proxy node 160 within the domain 110.

When an initial communication commences with the domain node 120, thesequence number 150 can be assigned to a registration occurring betweenthe domain node 120 and the mobile device 140. Upon movement of themobile device 140 where other access nodes or access components 130become involved, a subsequent registration can occur with the domainnode 120. During the subsequent registration, the previous sequencenumber can be incremented and employed for the subsequent registration.The domain node 120 or other controlling node then employs the sequencedata 150 to track where messages should be routed across the domain 110and in view of the respective sequence data received. In this manner,out of order delivery problems associated with prior systems andprotocols is mitigated. As can be appreciated, sequence data 150 cantake on many forms. Thus, incrementing data or decrementing data can beconsidered sequential. Similarly, as with timestamp data, the sequencedata 150 does not have to employ consecutive sequence information aslong as in increasing or decreasing pattern is observed (e.g., 1,2,3, 4,5 . . . is sequential as is 13, 9, 7, 6, 2 . . . and so forth).

In one specific example, the system 100 can employ Proxy Mobile InternetProtocol (PMIP). Such mobile protocols are often employed with a networkdomain 110 that includes nodes such as access nodes and Local MobilityAnchors (LMA) for example that often employ the mobile IP protocols inconjunction with a domain protocol to manage the respective deviceswithin the domain 110. One such domain protocol is referred to as aNetwork-based Localized Mobility Management (NETLMM) protocol. In oneaspect, PMIP and NETLMM potentially suffer from out of order delivery ofmobility management messages from different access components 130 to thedomain node 120. If messages reach the domain node 120 out of order, thedomain node can send traffic to the wrong access component 130. Thus, inone example, PMIP/NETLMM messages from the access components 130 aretriggered by on the event of communication link creation as will bedescribed in more detail with respect to FIG. 2. This can take differentforms, including some form of an L2 connection request, e.g., AddressResolution Protocol (ARP), Neighbor Discovery (ND), Dynamic HostConfiguration Protocol (DHCP) or other protocol. Whatever the protocolemployed, an extension can be introduced in which the mobile device 140or a network based proxy 160 provides a sequence data 150 (ortimestamp). In this manner, the mobile device 140 (or its network proxy)indicates the order in which the communications links are created. Theaccess components 130 then copy this sequence data 150 (or timestamp) inthe mobility management message it sends to the LMA or domain node 120.The sequence data 150 allows the domain node 120 to detect out of orderdelivery of PMIP/NETLMM messages which prevents misdirection of trafficthrough the access components 130.

It is noted that the terminal or mobile device 140, can be, forinstance, a module such as an SD card, a network card, a wirelessnetwork card, a computer (including laptops, desktops, personal digitalassistants PDAs), mobile phones, smart phones, or any other suitableterminal that can be utilized to access a network. The mobile device 140accesses the network by way of an access component 130. In one example,a connection between the mobile device 140 and the access components 130may be wireless in nature, in which access components may be a basestation and the mobile device may be a wireless terminal. For instance,the device 140 and access component 130 may communicate by way of anysuitable wireless protocol, including but not limited to Time DivisionalMultiple Access (TDMA), Code Division Multiple Access (CDMA), FrequencyDivision Multiple Access (FDMA), Orthogonal Frequency DivisionMultiplexing (OFDM), FLASH OFDM, Orthogonal Frequency Division MultipleAccess (OFDMA), or any other suitable protocol.

Similarly to the mobile device 140, the access components 130 can be anaccess node associated with a wired network or a wireless network. Tothat end, access component 130 can be, for instance, a router, a switch,or the like. The access component 130 can include one or moreinterfaces, e.g., communication modules, for communicating with othernetwork nodes. Additionally, the access component 130 may be a basestation (or wireless access point) in a cellular type network, whereinbase stations (or wireless access points) are utilized to providewireless coverage areas to a plurality of subscribers. Such basestations (or wireless access points) can be arranged to providecontiguous areas of coverage to one or more cellular phones and/or otherwireless terminals.

Referring now to FIG. 2, an example network access system 200 isillustrated that can employ sequence data to form communications linksand facilitate message ordering. The system 200 includes a localmobility anchor (LMA) 210 that communicates to one or more access points220 to a mobile device 230. The system 200 employs a mobile specificSequence Number to order registrations from different access points (orrouters) 220 to the LMA 210. At 240, a sequence number is provided bythe mobile itself device 230 of a network based proxy described below.The system 200 shows how sequence numbers such as shown at 240 can beemployed for registration messages from an access point 2 (AP2) at 250and an access point 3 (AP3) at 260 can be ordered. In this example, themobile device 240 includes the Sequence Number in a link creationmessage at reference numeral 240.

The link creation message at 240 can be a message that triggers a NetLMMregistration from the respective AP 220, for example although otherprotocols than NetLMM can be employed. The link creation message 240 istypically is a link layer message (e.g., a connection request), an ARPrequest message, a Neighbor Discovery message or other message that maybe used to trigger such registrations. As shown at 270, a registrationis formed with the LMA 210 based off the sequence number generated at240. If the mobile is moved, where another access point 3 at 280 isinvolved, a subsequent link message can be created at 284 with a newsequence number, where the subsequent sequence information can beemployed for a subsequent registration show at 290. The sequence numbersreceived by the registrations at 270 and 290 are then employed tofacilitate orderly communications between the LMA 210 and the accesspoint 2 at 250 and the access point 3 at 280.

Now referring to FIG. 3, a message flow diagram 300 illustrates theexample messages and registrations depicted in FIG. 2. As shown, thediagram includes a mobile 310, an access point 2 (AP2) 312, an accesspoint 3 (AP3) 314, and an LMA 316. At 320, a link creation messagehaving sequence data is sent between the mobile 310 and AP2 312. At 330,AP2 312 generates a request 330 to the LMA 216. At 340, the LMA 316generates a request response to AP2 312 and forms a tunnel channel at350 with AP2. When a subsequent access point is required by the mobile310, a subsequent creation link is formed at 360 between the mobile 310and AP3 314 with a different sequence number. Proceeding to 370, asubsequent request employing the subsequent sequence number is generatedto the LMA 316 from AP3 314. At 380, the LMA 316 generates a requestresponse in view of the subsequent request, and at 390 a new tunnelchannel is formed between AP3 214 and the LMA.

Turning to FIG. 4, an example proxy-based system 400 is illustrated. Thesystem 400 shows how sequence data can be employed to order registrationmessages by using a Proxy Mobile 410 in a network 420. The system 400can be used in Network Controlled handoffs where a network controller(not shown) (collocated or in communication with a Proxy Mobile)receives signal to noise ratio (SNR) (or other link quality parameter)reports at 424 from a mobile 430 for the different access points 440 themobile is in the region of. Based on such signal quality measurements,the Network Controller commands the mobile 430 to move at 434, say fromAP2 at 450 to AP3 at 460 in this example. Thus, the Proxy Mobile 410then sends a Sequence Number to AP3 460 which is incremented from thelast Sequence Number used when the link with AP2 at 450 was established.The AP3 460 then includes the Sequence Number in the Registrationmessage sent to the LMA at 470.

Referring to FIG. 5, a message flow diagram 500 illustrates examplemessages and registrations depicted in FIG. 4. In the diagram 500,dashed lines represent optional messages that can be provided in variousways. A mobile 502 creates an initial link 501 with AP2 504. Then, AP2504 initiates a Sequence Number 508 with a Network Controller (NC)/ProxyMobile (PM) 510. It is noted that the NC and PM at 510 may be collocatedor may be independent but communicating processes. In one aspect, AP2504 uses the Sequence Number 508 provided by NC/PM 510 to perform a PMIPregistration with an LMA 514. The LMA 514 forms a tunnel now at 520 forthe mobile points to AP2 504.

The Mobile 502 sends link measurement reports at 530 (e.g., SNR reports)to the NC/PM 510. The NC/PM 510 makes a decision that AP3 at 540 is amore suitable access point for the Mobile 502 and sends a command at 534to the mobile 502 to instruct it to move to AP3 540. The NC/PM 510 alsosends a new Sequence Number 550 to AP3 540. The mobile 502 creates alink 560 to AP3 540 and the AP3 performs a PMIP registration—this timewith the new Sequence Number. A tunnel 570 now points to AP3 540 forthat mobile 502. The Sequence Number can be a number or a timestamp orother incrementing ID as noted previously. A PMIP protocol is utilizedas an example implementation of NetLMM, where NetLMM may be implementedwith other message types between an access router (also called a MAG)and the LMA 514. Another variant of this message exchange is thatinstead of PMIP, regular MIP can be used with the NC/PM node 510providing a Mobile IP client and the LMA providing a Mobile IP HomeAgent. The APs may optionally be Mobile IP Foreign agents, if desired.

Referring to FIG. 6, a methodology 600 relating to message ordering andregistration is illustrated. While, for purposes of simplicity ofexplanation, the methodology is shown and described as a series of acts,it is to be understood and appreciated that the methodology is notlimited by the order of acts, as some acts may, in accordance with oneor more embodiments, occur in different orders and/or concurrently withother acts from that shown and described herein. For example, thoseskilled in the art will understand and appreciate that a methodologycould alternatively be represented as a series of interrelated states orevents, such as in a state diagram. Moreover, not all illustrated actsmay be utilized to implement a methodology in accordance with theclaimed subject matter.

Proceeding to 602, the process 600 begins where an initial registrationis performed at 604 when a mobile device communicates via an access nodeto a domain node such as a local mobility anchor (LMA). At 606, inaccordance with the registration, a sequence number is generated by thedevice that will be employed for communications with duringcommunications with the respective access node registered at 604. At608, when the mobile device moves out of range of the previous accesspoint and into range of another access point, a subsequent registrationis performed with the LMA through the new access point. At 610, a newsequence number is assigned for the subsequent registration at 608 bythe mobile device. As noted above, the sequence numbers can take theform of incremental data, decremented data, or time stamp data forexample. Also, if yet another access point is encountered, yet anotherregistration can be performed along with generation of yet anothersequence number.

At 612, the mobile device employs the respective sequence number whencommunicating with a given access point. For instance, if sequencenumber 1 is generated when registering to access point 1, then sequencenumber 1 is employed as part of the messaging protocol for futurecommunications through access point 1. Similarly, if sequence number 2is generated when registering through access point 2, then sequencenumber 2 is employed by the mobile device as part of its messagingprotocol for further communications through access point 2. In thismanner, message ordering can be achieved and effects such as nodeping-pong are mitigated. As can be appreciated, more than two nodes canbe registered having additional sequence numbers as may be necessary forthe additional access points.

Turning now to FIGS. 7 and 8 collectively, systems are provided thatrelate to sequence ordering with respect to a terminal, operatornetworks, access nodes, and traffic flows therewith. The systems arerepresented as a series of interrelated functional blocks, which canrepresent functions implemented by a processor, software, hardware,firmware, or any suitable combination thereof.

Referring specifically to FIG. 7, a system 700 that facilitatescommunications from a mobile device. The system 700 includes a logicalmodule 702 for registering with a network domain node via an accesspoint and a logical module 704 for generating sequence data whenregistering with the network domain node. A logical module 706 can beemployed for processing the sequence data to communicate through theaccess point.

Now referring to FIG. 8, a system 800 that facilitates communicationsfrom a network domain node. The system 800 includes a logical module 802for registering a mobile device via an access point and a logical module804 for processing sequence data when registering with the mobiledevice. A logical module 806 can be utilized for decoding the sequencedata during subsequent communications with the mobile device.

FIG. 9 illustrates a communications apparatus 900 that can be a wirelesscommunications apparatus, for instance, such as a wireless terminal.Additionally or alternatively, communications apparatus 900 can beresident within a wired network. Communications apparatus 900 caninclude memory 902 that can retain instructions for configuring suchapparatus with respect to quality of service (QoS) data and sequencedata for a terminal (and traffic flows associated therewith).Additionally, communications apparatus 900 may include a processor 904that can execute instructions within memory 902 and/or instructionsreceived from another network device, wherein the instructions canrelate to configuring or operating the communications apparatus 900 or arelated communications apparatus.

To provide additional context for one or more embodiments describedherein, FIG. 11 is provided to illustrate an example communicationsystem 1100 that comprises a plurality of nodes interconnected bycommunications links. The system 1100 may use Orthogonal FrequencyDivision Multiplexing (OFDM) signals to communicate information overwireless links. However, other types of signals, e.g., Code DivisionMultiple Access (CDMA) signals or Time Division Multiple Access (TDMA)signals, are also contemplated (together with signals utilized inland-based networks). Nodes in the communication system 1100 exchangeinformation using signals, e.g., messages, based on communicationprotocols, e.g., the Internet Protocol (IP). The communications links ofthe system 1100 may be implemented, for example, using wires, fiberoptic cables, and/or wireless communications techniques. The system 1100includes a plurality of end nodes 1102-1112, which access thecommunication system 1100 by way of a plurality of access nodes1114-1118. End nodes 1102-1112 may be, e.g., wireless communicationdevices or terminals, and the access nodes 1114-1118 may be, e.g.,wireless access routers or base stations. Communication system 1100 alsoincludes a number of other nodes 1120-1130 that are used to provideinterconnectivity or to provide specific services or functions.

Communications system 1100 depicts a network 1160 that includes accesscontrol node 1120, mobility support node 1122, policy control node 1124,and application server node 1126, all of which are connected to anintermediate network node 1128 by a corresponding network link1132-1138, respectively. In some embodiments, the access control node,e.g., a Remote Authentication Dial In User Service (RADIUS) or Diameterserver, supports authentication, authorization, and/or accounting of endnodes and/or services associated with end nodes. In some embodiments,mobility support node 1122, e.g., a Mobile IP home agent and/or contexttransfer server, supports mobility, e.g., handoff, of end nodes betweenaccess nodes, e.g., by way of redirection of traffic to/from end nodesand/or transfer of state associated with end nodes between access nodes.In some embodiments, policy control node 1124, e.g., a policy server orPolicy Decision Point (PDP), supports policy authorization for servicesor application layer sessions. In some embodiments, application servernode 1126, e.g., a Session Initiation Protocol server, streaming mediaserver, or other application layer server, supports session signalingfor services available to end nodes and/or provides services or contentavailable to end nodes.

Intermediate network node 1128 in network 1160 providesinterconnectivity to network nodes that are external from theperspective of network 1160 by way of network link 1134. Network link1134 is connected to intermediate network node 1130, which providesfurther connectivity to access nodes 1114, 1116, and 1118 by way ofnetwork links 1136-1140, respectively. Each access node 1114-1118 isdepicted as providing connectivity to end nodes 1102-1112, respectively,by way of corresponding access links 1142-1152, respectively. Incommunication system 1100, each access node 1114-1118 is depicted asusing wireless technology, e.g., wireless access links, to provideaccess. Wired technology may also be utilized, however, in connectionwith provision of access. A radio coverage area, e.g., communicationscells 1154-1158 of each access node 1114-1118, is illustrated as acircle surrounding the corresponding access node.

Communication system 1100 can be used as a basis for the description ofvarious embodiments described herein. Alternative embodiments includevarious network topologies, where a number and type of nodes (includingnetwork nodes, access nodes, end nodes, as well as various control,support, and server nodes), a number and type of links, andinterconnectivity between various nodes may differ from that ofcommunication system 1100. Additionally, some of the functional entitiesdepicted in communication system 1100 may be omitted or combined.Location or placement of these functional entities may also be varied.

FIG. 12 provides an illustration of an example end node 1200, e.g.,wireless terminal. End node 1200 is a representation of an apparatusthat may be used as any one of end nodes 1102-1112 (FIG. 11). End node1200 includes a processor 1202, a wireless communication interfacemodule 1204, a user input/output interface 1206 and memory 1208 coupledtogether by a bus 1210. Accordingly, by way of bus 1210, the variouscomponents of the end node 1200 can exchange information, signals anddata. Components 1202-1208 of end node 1200 can be located inside ahousing 1212.

Wireless communication interface module 1204 provides a mechanism bywhich the internal components of end node 1200 can send and receivesignals to/from external devices and network nodes, e.g., access nodes.Wireless communication interface module 1204 includes, e.g., a receivermodule 1214 with a corresponding receiving antenna 1216 and atransmitter module 1218 with a corresponding transmitting antenna 1220used for coupling end node 1200 to other network nodes, e.g., by way ofwireless communications channels.

End node 1200 also includes a user input device 1222, e.g., keypad, anda user output device 1224, e.g., display, which are coupled to bus 1210through user input/output interface 1206. Thus, user input/outputdevices 1222 and 1224 can exchange information, signals and data withother components of end node 1200 by way of user input/output interface1206 and bus 1210. User input/output interface 1206 and associateddevices 1222 and 1224 provide mechanisms by which a user can operate endnode 1200 to accomplish various tasks. In particular, user input device1222 and user output device 1224 provide functionality that allows auser to control end node 1200 and applications, e.g., modules, programs,routines and/or functions, that execute in memory 1208 of end node 1200.

Processor 1202, under control of various modules, e.g., routines,included in memory 1208 controls operation of end node 1200 to performvarious signaling and processing. The modules included in memory 1208are executed on startup or as called by other modules. Modules mayexchange data, information, and signals when executed. Modules may alsoshare data and information when executed. Memory 1208 of end node 1200includes a control signaling module 1226, an application module 1228,and a traffic control module 1230, which further includes configurationinformation 1232 and various additional modules.

Control signaling module 1226 controls processing relating to receivingand sending signals, e.g., messages, for controlling operation and/orconfiguration of various aspects of end node 1200 including, e.g.,traffic control module 1230 as well as configuration information 1232and various additional modules included. In some embodiments, controlsignaling module 1226 can include state information, e.g., parameters,status and/or other information, relating to operation of end node 1200and/or one or more signaling protocols supported by control signalingmodule 1226. In particular, control signaling module 1226 may includeconfiguration information, e.g., end node identification informationand/or parameter settings, and operational information, e.g.,information about current processing state, status of pending messagetransactions, etc.

Application module 1228 controls processing and communications relatingto one or more applications supported by end node 1200. In someembodiments, application module 1228 processing can include tasksrelating to input/output of information by way of the user input/outputinterface 1206, manipulation of information associated with anapplication, and/or receiving or sending signals, e.g., messages,associated with an application. In some embodiments, application module1228 includes state information, e.g., parameters, status and/or otherinformation, relating to operation of one or more applications supportedby application module 1228. In particular, application module 1228 mayinclude configuration information, e.g., user identification informationand/or parameter settings, and operational information, e.g.,information about current processing state, status of pending responses,etc. Applications supported by application module 1228 include, e.g.,Voice over IP (VoIP), web browsing, streaming audio/video, instantmessaging, file sharing, gaming, etc.

Traffic control module 1230 controls processing relating to receivingand sending data information, e.g., messages, packets, and/or frames,through wireless communication interface module 1204. The exampletraffic control module 1230 includes configuration information 1232 aswell as various additional modules that control various aspects of QoSfor packets and/or traffic flows, e.g., associated sequences of packets.Various additional modules are included, in some embodiments, to performparticular functions and operations as needed to support specificaspects of traffic control. Modules may be omitted and/or combined asneeded depending on the functional requirements of traffic control. Adescription of each additional module included in traffic control module1230 follows.

An admission control module 1234 maintains information relating toresource utilization/availability and determines if sufficient resourcesare available to support QoS parameters desirably associated withparticular traffic flows. Resource availability information maintainedby admission control module 1234 includes, e.g., packet and/or framequeuing capacity, scheduling capacity, as well as processing and memorycapacity needed to support one or more traffic flows. Control signalingmodule 1226, application module 1228, and/or other modules included inend node 1200 may query admission control module 1234 to determine ifsufficient resources are available to support a new or modified trafficflow, where the admission control determination is a function of QoSparameters of the particular traffic flow and QoS parameters definedwithin a profile. Configuration information 1232 can includeconfiguration information, e.g., parameters settings, that affect theoperation of admission control module 1234, e.g., an admission controlthreshold value that indicates percentage of resource that may beallocated prior to rejecting additional requests.

An uplink scheduler module 1236 controls processing relating totransmission scheduling, e.g., order and/or timing, and allocation oftransmission resources, e.g., information coding rate, transmission timeslots, and/or transmission power, for data information, e.g., messages,packets, and/or frames, to be sent by way of wireless communicationinterface module 1204, e.g., from end node 1200 to an access node.Uplink scheduler module 1236 can schedule transmissions and allocatetransmission resources as a function of QoS parameters associated withone or more traffic flows. In some embodiments, scheduling and/orresource allocation operations performed by uplink scheduler module 1236are additionally a function of channel conditions and other factors,e.g., power budget.

An uplink PHY/MAC module 1238 controls physical (PHY) layer and MediaAccess Control (MAC) layer processing relating to sending datainformation, e.g., messages, packets, and/or frames, by way of wirelesscommunication interface module 1204, e.g., from end node 1200 to anaccess node. For instance, operation of uplink PHY/MAC module 1238includes both sending and receiving control information, e.g., signalsor messages, to coordinate sending of data information, e.g., messages,packets, and/or frames. Configuration information 1232 can includeconfiguration information, e.g., parameters settings, that affect theoperation of uplink PHY/MAC module 1238, e.g., a frequency, band,channel, spreading code or hoping code to be used for transmissions, anidentifier associated with end node 1200, a request dictionaryprescribing use of an assignment request channel, etc.

An uplink LLC (ARQ) module 1240 controls Logical Link Control (LLC)layer processing relating to sending data information, e.g., messages,packets, and/or frames, through wireless communication interface module1204, e.g., from end node 1200 to an access node. Uplink LLC (ARQ)module 1240 includes processing associated with Automatic Repeat Request(ARQ) capabilities, e.g., retransmission of lost packets or frames.Uplink LLC (ARQ) module 1240 can, for instance, further includeprocessing relating to addition of an LLC header and/or trailer tohigher layer messages, e.g., packets, to provide additionalfunctionality, e.g., multi-protocol multiplexing/demultiplexing by wayof a type field or error detection through utilization of a checksumfield. Uplink LLC (ARQ) module 1240 can additionally performfragmentation of higher layer messages, e.g., packets, into multiplesub-portions, e.g., frames to be sent by uplink PHY/MAC module 1240.Configuration information 1232 can include configuration informationthat affect operation of uplink LLC (ARQ) module 1240, e.g., an ARQwindow size, maximum number of retransmissions, a discard timer, etc.

An uplink queue management module 1242 maintains information andcontrols processing relating to storage of data information to be sentby way of wireless communication interface module 1204, e.g., from endnode 1200 to an access node. Uplink queue management module 1242 can,for example, control storage of data information awaiting transmissionand maintain state information regarding data information awaitingtransmission on a per traffic flow basis, e.g., packets associated witheach traffic flow may be stored in separate queues. For instance, uplinkqueue management module 1242 supports a variety of queue managementtechniques and/or capabilities, e.g., head drop, tail drop, as well asvarious Active Queue Management (AQM) mechanisms such as Random EarlyDetection (RED). Configuration information 1232 can includeconfiguration information that affects operation of uplink queuemanagement module 1242, such as a queue limit, drop strategy, and/or AQMthresholds associated with one or more traffic flows.

An uplink classifier module 1244 controls processing relating toidentification of data information as belonging to particular trafficflows prior to being sent by way of the wireless communication interfacemodule 1204, e.g., from end node 1200 to an access node. In someembodiments, messages, packets, and/or frames to be sent throughutilization of wireless communication interface module 1204 areclassified as belonging to one of a variety of traffic flows by uplinkclassifier module 1244 based on inspection of one or more header and/orpayload fields. Results of classification by uplink classifier module1244 can affect the treatment of classified data information by uplinkqueue management module 1242 as well as other modules within memory1208. For example, the results may determine a particular queue themessage, packet, and/or frame will be associated with for storage andfurther affect subsequent processing such as scheduling. Configurationinformation can include configuration information that affect operationof uplink classifier module 1244, e.g., a set of one or more classifierfilter rules that prescribe criteria used to associate data information,e.g., messages, packets, and/or frames, as belonging to one or moretraffic flows.

A downlink PHY/MAC module 1246 controls PHY layer and MAC layerprocessing relating to receiving data information by way of wirelesscommunication interface module 1204. Operation of downlink PHY/MACmodule 1246 can include both sending and receiving control informationto coordinate receiving of data information. Configuration information1204 can include configuration information that affect operation ofdownlink PHY/MAC module 1246, e.g., a frequency, band, channel,spreading code or hoping code to be used for reception, an identifierassociated with end node 1200, etc.

A downlink LLC (ARQ) module 1248 controls LLC layer processing relatingto receiving data information by way of wireless communication interfacemodule 1204. Downlink LLC (ARQ) module 1248 includes processingassociated with ARQ capabilities, e.g., retransmission of lost packetsor frames. For example, downlink LLC (ARQ) module 1248 can furtherinclude processing relating to an LLC header and/or trailer thatencapsulates higher layer messages, which provides additionalfunctionality, e.g., multi-protocol multiplexing/demultiplexing througha type field or error detection by way of a checksum field. Downlink LLC(ARQ) module 1248 can also perform reassembly of frames received by thedownlink PHY/MAC module 1246 into higher layer messages. Configurationinformation 1232 can, and in some embodiments does, includeconfiguration information, e.g., parameters settings, that affectoperation of downlink LLC (ARQ) module 1248, e.g., an ARQ window size,maximum number of retransmissions, a discard timer, etc.

FIG. 13 provides a detailed illustration of an example access node 1300implemented in accordance with the present invention. The access node1300 is a detailed representation of an apparatus that may be used asany one of the access nodes 1114-1118 depicted in FIG. 11. In the FIG.13 embodiment, access node 1300 includes a processor 1302, memory 1304,a network/internetwork interface module 1306 and a wirelesscommunication interface module 1308, coupled together by bus 1310.Accordingly, by way of bus 1310 the various components of access node1300 can exchange information, signals and data. The components1302-1310 of access node 1300 are located inside a housing 1312.

Network/internetwork interface module 1306 provides a mechanism by whichthe internal components of access node 1300 can send and receive signalsto/from external devices and network nodes. Network/internetworkinterface module 1306 includes a receiver module 1314 and a transmittermodule 1316 used for coupling node 1300 to other network nodes, e.g.,through copper wires or fiber optic lines. Wireless communicationinterface module 1308 also provides a mechanism by which the internalcomponents of access node 1300 can send and receive signals to/fromexternal devices and network nodes, e.g., end nodes. Wirelesscommunication interface module 1308 includes, e.g., a receiver module1318 with a corresponding receiving antenna 1320 and a transmittermodule 1322 with a corresponding transmitting antenna 1324. Wirelesscommunication interface module 1308 is used for coupling access node1300 to other nodes, e.g., by way of wireless communication channels.

Processor 1302 under control of various modules, e.g., routines,included in memory 1304 controls operation of access node 1300 toperform various signaling and processing. The modules included in memory1304 are executed on startup or as called by other modules. Modules mayexchange data, information, and signals when executed. Modules may alsoshare data and information when executed. In the FIG. 13 embodiment,memory 1304 of access node 1300 includes a control signaling module 1326and a traffic control module 1328, which further includes configurationinformation 1330 and various additional modules 1332-1354.

Control signaling module 1326 controls processing relating to receivingand sending signals, e.g., messages, for controlling operation and/orconfiguration of various aspects of access node 1300 including, e.g.,traffic control module 1328 as well as configuration information 1330and the various additional modules included therein 1332-1354. Forinstance, control signaling module 1326 includes state information,e.g., parameters, status and/or other information, relating to operationof access node 1300 and/or one or more signaling protocols supported bycontrol signaling module 1326. In particular, control signaling module1326 may include configuration information, e.g., access nodeidentification information and/or parameter settings, and operationalinformation, e.g., information about current processing state, status ofpending message transactions, etc.

Traffic control module 1328 controls processing relating to receivingand sending data information, e.g., messages, packets, and/or frames, byway of wireless communication interface module 1308. For instance,traffic control module can include configuration information 1330 aswell as various additional modules 1332-1354 that control variousaspects of quality of service for packets and/or traffic flows, e.g.,associated sequences of packets. In some embodiments, traffic controlmodule 1328 includes state information, e.g., parameters, status and/orother information, relating to operation of access node 1300, trafficcontrol module 1328, and/or one or more of the various additionalmodules included therein 1332-1354. Configuration information 1330,e.g., parameter settings, determines, affects and/or prescribesoperation of traffic control module 1328 and/or the various additionalmodules included therein 1332-1354. The various additional modules areincluded, in some embodiments, to perform particular functions andoperations as needed to support specific aspects of traffic control. Invarious embodiments, modules may be omitted and/or combined as neededdepending on the functional requirements of traffic control. Adescription of each additional module included in traffic control module1328 follows.

Admission control module 1332 maintains information relating to resourceutilization/availability and determines if sufficient resources areavailable to support quality of service requirements of particulartraffic flows. Resource availability information maintained by admissioncontrol module 1332 includes, e.g., packet and/or frame queuingcapacity, scheduling capacity, as well as processing and memory capacityneeded to support one or more traffic flows. Control signaling module1326 and/or other modules included in access node 1300 can queryadmission control module 1332 to determine if sufficient resources areavailable to support a new or modified traffic flow, where the admissioncontrol determination is a function of the quality of servicerequirements of the particular traffic flow and/or the availableresources. Configuration information 1330 can include configurationinformation, e.g., parameters settings, that affect the operation ofadmission control module 1332, e.g., an admission control thresholdvalue that indicates the percentage of resource that may be allocatedprior to rejecting additional requests.

Uplink scheduler module 1334 controls processing relating totransmission scheduling, e.g., order and/or timing, and allocation oftransmission resources, e.g., information coding rate, transmission timeslots, and/or transmission power, for data information, e.g., messages,packets, and/or frames, to be sent from one or more end nodes to theaccess node by way of wireless interface module 1308. Uplink schedulermodule 1334 can schedule transmissions and allocate transmissionresources as a function of the quality of service requirements and/orconstraints associated with one or more traffic flows and/or one or moreend nodes. Configuration information 1330 can include configurationinformation that affect the operation of uplink scheduler module 1334,e.g., a priority, rate bound, latency bound, and/or sharing weightassociated with one or more traffic flows and/or end nodes. In someembodiments, scheduling and/or resource allocation operations performedby uplink scheduler module 1334 are additionally a function of channelconditions and other factors, e.g., power budget.

Downlink scheduler module 1336 controls processing relating totransmission scheduling, e.g., order and/or timing, and allocation oftransmission resources, e.g., information coding rate, transmission timeslots, and/or transmission power, for data information, e.g., messages,packets, and/or frames, to be sent from access node 1300 to one or moreend nodes through wireless interface module 1308. Downlink schedulermodule 1336 can schedule transmissions and allocate transmissionresources as a function of the quality of service requirements and/orconstraints associated with one or more traffic flows and/or one or moreend nodes. Configuration information 1330 can include configurationinformation that affects the operation of downlink scheduler module1336, e.g., a priority, rate bound, latency bound, and/or sharing weightassociated with one or more traffic flows and/or end nodes. In someembodiments, scheduling and/or resource allocation operations performedby the downlink scheduler module 1336 are additionally a function ofchannel conditions and other factors, e.g., power budget.

Uplink traffic conditioner module 1338 controls processing relating totraffic conditioning, e.g., metering, marking, policing, etc., for datainformation, e.g., messages, packets, and/or frames, received by way ofwireless interface module 1308, e.g., from an end node to access node1300. Uplink traffic conditioner module 1338 can condition traffic,e.g., meter, mark and/or police, as a function of the quality of servicerequirements and/or constraints associated with one or more trafficflows and/or one or more end nodes. Configuration information 1330 caninclude configuration information that affects the operation of uplinktraffic conditioner module 1338, e.g., a rate bound, and/or markingvalue associated with one or more traffic flows and/or end nodes.

Uplink classifier module 1340 controls processing relating toidentification of data information, e.g., messages, packets, and/orframes, received through wireless interface module 1308, e.g., from anend node to access node 1300, as belonging to particular traffic flowsprior to being processed by uplink traffic conditioner module 1338. Insome embodiments, messages, packets, and/or frames received throughwireless communication interface module 1308 are classified as belongingto one of a variety of traffic flows by uplink classifier module 1340based on inspection of one or more header and/or payload fields. Theresults of classification by uplink classifier module 1340 can affectthe treatment of the classified data information, e.g., messages,packets, and/or frames, by uplink traffic conditioner module 1338, e.g.,the results may determine a particular data structure or state machinethe message, packet, and/or frame will be associated with and furtheraffect subsequent processing such as metering, marking, and/or policing.Configuration information 1330 can include configuration informationthat affects the operation of uplink classifier module 1340, e.g., a setof one or more classifier filter rules that prescribe criteria used toassociate data information, e.g., messages, packets, and/or frames, asbelonging to one or more traffic flows.

Uplink LLC (ARQ) module 1342 controls LLC layer processing relating toreceiving data information, e.g., packets and/or frames, by way ofwireless communication interface module 1308, e.g., from an end node toaccess node 1300. Uplink LLC (ARQ) module 1342 includes processingassociated with ARQ capabilities, e.g., retransmission of lost packetsor frames. In some embodiments, uplink LLC (ARQ) module 1342 furtherincludes processing relating to an LLC header and/or trailer thatencapsulates higher layer messages, e.g., packets, which providesadditional functionality, e.g., multi-protocolmultiplexing/demultiplexing through a type field or error detection byway of a checksum field. Uplink LLC (ARQ) module 1342 can also performreassembly of frames received by uplink PHY/MAC module 1344 into higherlayer messages, e.g., packets. The configuration information 1330 caninclude configuration information that affects the operation of uplinkLLC (ARQ) module 1342, e.g., an ARQ window size, maximum number ofretransmissions, a discard timer, etc.

Uplink PHY/MAC module 1344 controls PHY layer and MAC layer processingrelating to receiving data information, e.g., packets and/or frames, byway of wireless communication interface module 1308, e.g., from an endnode to access node 1300. In some embodiments, operation of uplinkPHY/MAC module 1344 includes both sending and receiving controlinformation, e.g., signals or messages, to coordinate receiving of datainformation, e.g., messages, packets, or frames. Configurationinformation 1330 can include configuration information that affects theoperation of uplink PHY/MAC module 1344, e.g., a frequency, band,channel, spreading code or hopping code to be used for reception, anidentifier associated with access node 1300, etc.

Downlink classifier module 1346 controls processing relating toidentification of data information, e.g., messages, packets, and/orframes, as belonging to particular traffic flows prior to being sentthrough wireless communication interface module 1308, e.g., from accessnode 1300 to an end node. In some embodiments, messages, packets, and/orframes to be sent by way of wireless communication interface module 1308are classified as belonging to one of a variety of traffic flows bydownlink classifier module 1346 based on inspection of one or moreheader and/or payload fields. The results of classification by downlinkclassifier module 1346 can affect the treatment of the classified datainformation, e.g., messages, packets, and/or frames, by downlink queuemanagement module 1350 and other modules 1348, 1352, and 1354, e.g., theresults may determine a particular queue the message, packet, and/orframe will be associated with for storage and further affect subsequentprocessing such as scheduling. Configuration information 1330 caninclude configuration information, e.g., parameters settings, thataffect the operation of downlink classifier module 1346, e.g., a set ofone or more classifier filter rules that prescribe criteria used toassociate data information, e.g., messages, packets, and/or frames, asbelonging to one or more traffic flows.

Downlink traffic conditioner module 1348 controls processing relating totraffic conditioning, e.g., metering, marking, policing, etc., for datainformation, e.g., messages, packets, and/or frames, to be sent by wayof wireless interface module 1308, e.g., from access node 1300 to an endnode. Downlink traffic conditioner module 1348 can condition traffic,e.g., meter, mark and/or police, as a function of the quality of servicerequirements and/or constraints associated with one or more trafficflows and/or one or more end nodes. Configuration information 1330 caninclude configuration information that affects the operation of downlinktraffic conditioner module 1348, e.g., a rate bound, and/or markingvalue associated with one or more traffic flows and/or end nodes.

Downlink queue management module 1350 maintains information and controlsprocessing relating to storage of data information, e.g., messages,packets, and/or frames, to be sent by way of wireless communicationinterface module 1308, e.g., from access node 1300 to an end node.Downlink queue management module can control storage of data informationawaiting transmission and maintain state information regarding datainformation awaiting transmission on a per traffic flow basis, e.g.,packets associated with each traffic flow may be stored in separatequeues. In some embodiments of, Downlink queue management module 1350supports a variety of queue management techniques and/or capabilities,e.g., head drop, tail drop, as well as various AQM mechanisms such asRED. Configuration information 1330 can include configurationinformation that affects the operation of downlink queue managementmodule 1350, e.g., a queue limit, drop strategy, and/or AQM thresholdsassociated with one or more traffic flows.

Downlink LLC (ARQ) module 1352 controls LLC layer processing relating tosending data information, e.g., messages, packets, and/or frames, by wayof wireless communication interface module 1308, e.g., from access node1300 to an end node. Downlink LLC (ARQ) module 1352 includes processingassociated with ARQ capabilities, e.g., retransmission of lost packetsor frames. In some embodiments, downlink LLC (ARQ) module 1352 furtherincludes processing relating to the addition of an LLC header and/ortrailer to higher layer messages, e.g., packets, to provide additionalfunctionality, e.g., multi-protocol multiplexing/demultiplexing througha type field or error detection by way of a checksum field. Downlink LLC(ARQ) module 1352 can also perform fragmentation of higher layermessages, e.g., packets, into multiple sub-portions, e.g., frames to besent by downlink PHY/MAC module 1354. Configuration information 1330 caninclude configuration information that affects the operation of downlinkLLC (ARQ) module 1352, e.g., an ARQ window size, maximum number ofretransmissions, a discard timer, etc.

Downlink PHY/MAC module 1354 controls PHY layer and MAC layer processingrelating to sending data information, e.g., messages, packets, and/orframes, by way of wireless communication interface module 1308, e.g.,from access node 1300 to an end node. In some embodiments, operation ofdownlink PHY/MAC module 1354 includes both sending and receiving controlinformation, e.g., signals or messages, to coordinate sending of datainformation, e.g., messages, packets, or frames. Configurationinformation 1330 can include configuration information that affects theoperation of downlink PHY/MAC module 1354, e.g., a frequency, band,channel, spreading code or hoping code to be used for transmissions, anidentifier associated with the access node 1300, etc.

FIG. 14 illustrates example signaling and traffic flows between variousmodules included in example end node 1200 and example access node 1300.The FIG. 14 end node 1200 and FIG. 14 access node 1300 are simplifiedrepresentations of the FIG. 12 end node 1200 and FIG. 13 access node1300, respectively. The FIG. 14 example shows application module 1228sending and receiving data information, e.g., traffic flows comprising asequence of messages, packets, or frames. In the context of the FIG. 11example system, the FIG. 14 end node 1200 may be any one of end nodes1102-1112 depicted in FIG. 11 and the application module 1228 includedin the FIG. 14 end node 1200 may be exchanging data information withanother node in the system, e.g., another end node 1102-1112 or theapplication server node 1126 as depicted in FIG. 11. In FIG. 14 and thesubsequent description, the node with which the FIG. 14 end node 1200 isexchanging data information is referred to as the corresponding node.

The data information, e.g., traffic flows comprising a sequence ofmessages, packets, or frames, sent from the application module 1228 inthe end node 1200 to a corresponding node is shown by a sequence ofarrows 1402-1408 to proceed through a sequence of modules 1238-1244included in end node 1200 for processing, after which the datainformation is sent from the end node 1200 to the access node 1300,e.g., by way of wireless communication interface module 1204. Followingreception by access node 1300, e.g., by way of wireless communicationinterface module 1308, the data information, e.g., traffic flowscomprising a sequence of messages, packets, or frames, sent from theapplication module 1228 in end node 1200 to the corresponding node isshown by a sequence of arrows 1410-1418 to proceed through a sequence ofmodules 1338-1344 included in access node 1300 for processing, prior tobeing forwarded from the access node 1300 toward the corresponding node,e.g., directed in accordance with routing information to an intermediatenode connected to the access node by way of network/internetworkinterface module 1306.

The data information, e.g., traffic flows comprising a sequence ofmessages, packets, or frames, sent from a corresponding node toapplication module 1228 in end node 1228 is shown by a sequence ofarrows 1420-1428 to be received by access node 1300, e.g., by way ofnetwork/internetwork interface module 1306, and then to proceed througha sequence of modules 1346-1354 included in access node 1300 forprocessing, after which the data information is sent from the accessnode 1300 to the end node 1200, e.g., via the wireless communicationinterface module 1308. Following reception by end node 1200, e.g., byway of wireless communication interface module 1204, the datainformation, e.g., traffic flows comprising a sequence of messages,packets, or frames, sent from the corresponding node to applicationmodule 1228 in end node 1200 is shown by a sequence of arrows 1430-1434to proceed through a sequence of modules 1246 and 1248 included in endnode 1200 for processing, prior to being delivered to the applicationmodule 1228 in end node 1200.

In addition to the exchange of data information, e.g., traffic flows,FIG. 14 also depicts the exchange of control information, e.g.,signaling flows and/or communication interfaces. In particular, the FIG.14 example depicts the exchange of control information between controlsignaling module 1326 and traffic control module 1328 included in accessnode 1300. Similarly, the FIG. 14 example depicts the exchange ofcontrol information between control signaling module 1226 and thetraffic control module 1230 included in the end node 1200. In bothaccess node 1300 and end node 1200, exchange of control informationbetween the modules as shown allows the respective control signalingmodule 1326/1226 in the access/end node 1300/1200 to affect, e.g., set,modify, and/or monitor, the configuration and/or operation of thevarious modules included in the respective traffic control module1328/1230, as needed to provide the proper quality of service treatmentof the data information, e.g., traffic flows, to/from the applicationmodule 1228 in the end node 1200.

The exchange of control information, e.g., signaling flows and/orcommunication interfaces, is also shown a) between another node andcontrol signaling module 1326 in access node 1300, b) betweenapplication module 1228 in end node 1200 and control signaling module1226 in end node 1200, and c) between the respective control signalingmodules 1326/1226 in access node 1300 and end node 1200. These exchangesof control information, e.g., signaling flows and/or communicationinterfaces, enable the configuration and/or operation of traffic controlmodules 1328/1230 in both access node 1300 and the end node 1200 to beaffected by a) one or more additional nodes, e.g. the access controlnode 1120 and/or application server node 1126, b) application module1228 in end node 1200, or c) a combination of one or more additionalnodes and the application module 1228 in end node 1200. Variousembodiments of the present invention may, and do, support all or only asubset of the depicted control information exchanges as needed.

What has been described above includes examples of one or moreembodiments.

It is, of course, not possible to describe every conceivable combinationof components or methodologies for purposes of describing theaforementioned embodiments, but one of ordinary skill in the art mayrecognize that many further combinations and permutations of variousembodiments are possible. Accordingly, the described embodiments areintended to embrace all such alterations, modifications and variationsthat fall within the spirit and scope of the appended claims.Furthermore, to the extent that the term “includes” is used in eitherthe detailed description or the claims, such term is intended to beinclusive in a manner similar to the term “comprising” as “comprising”is interpreted when employed as a transitional word in a claim.

1. A communications method by a mobile device, comprising: communicatingover a first path between the mobile device and a first access point,wherein communication over the first path is associated with a firstsequence number; and communicating over a second path between the mobiledevice and a second access point, wherein communication over the secondpath is associated with a second sequence number, wherein the secondsequence number is different from the first sequence number, and whereinthe mobile device communicates over the first path and the second pathsimultaneously.
 2. The method of claim 1, wherein: communicating overthe first path comprises communicating one or more first packets overthe first path according to a messaging protocol, and communicating overthe second path comprises communicating one or more second packets overthe second path according to the messaging protocol.
 3. The method ofclaim 2, wherein: the first sequence number is employed as part of themessaging protocol for the one or more first packets communicated overthe first path, and the second sequence number is employed as part ofthe messaging protocol for the one or more second packets communicatedover the second path.
 4. The method of claim 1, wherein: the firstsequence number is generated when the mobile device registers with thefirst access point associated with the first path, and the secondsequence number is generated when the mobile device registers with thesecond access point associated with the second path.
 5. The method ofclaim 1, further comprising: generating the first sequence number; andgenerating the second sequence number.
 6. The method of claim 1,wherein: the first sequence number is associated with the first accesspoint, and the second sequence number is associated with the secondaccess point.
 7. The method of claim 1, wherein: communicating over thefirst path comprises employing the first sequence number for thecommunication over the first path from a time the first path isestablished until a time when the first path is terminated; andcommunicating over the second path comprises employing the secondsequence number for the communication over the second path from a timethe second path is established until a time when the second path isterminated.
 8. The method of claim 1, further comprising: employing, bythe mobile device, the first sequence number for further communicationof the mobile device with the first access point through the first path;and employing the second sequence number for further communication ofthe mobile device with the second access point through the second path,the first sequence number and the second sequence number for orderingmessages sent on the first path and the second path.
 9. The method ofclaim 1, further comprising: establishing a third path between themobile device and a third access point; and communicating over the thirdpath, wherein communication over the third path is associated with athird sequence number, and wherein the third sequence number isdifferent from the first sequence number and the second sequence number.10. The method of claim 9, further comprising: performing a handoverfrom the first path or the second path to the third path.
 11. A mobiledevice, comprising: a memory; at least one transceiver; and at least oneprocessor communicatively coupled to the memory and the at least onetransceiver, the at least one processor configured to: communicate, viathe at least one transceiver, over a first path between the mobiledevice and a first access point, wherein communication over the firstpath is associated with a first sequence number; and communicate, viathe at least one transceiver, over a second path between the mobiledevice and a second access point, wherein communication over the secondpath is associated with a second sequence number, wherein the secondsequence number is different from the first sequence number, and whereinthe mobile device communicates over the first path and the second pathsimultaneously.
 12. The mobile device of claim 11, wherein: communicate,via the at least one transceiver, over the first path comprisescommunicating one or more first packets over the first path according toa messaging protocol, and communicate, via the at least one transceiver,over the second path comprises communicating one or more second packetsover the second path according to the messaging protocol.
 13. The mobiledevice of claim 12, wherein: the first sequence number is employed aspart of the messaging protocol for the one or more first packetscommunicated over the first path, and the second sequence number isemployed as part of the messaging protocol for the one or more secondpackets communicated over the second path.
 14. The mobile device ofclaim 11, wherein: the first sequence number is generated when themobile device registers with the first access point associated with thefirst path, and the second sequence number is generated when the mobiledevice registers with the second access point associated with the secondpath.
 15. The mobile device of claim 11, wherein the at least oneprocessor is further configured to: generate the first sequence number;and generate the second sequence number.
 16. The mobile device of claim11, wherein: the first sequence number is associated with the firstaccess point, and the second sequence number is associated with thesecond access point.
 17. The mobile device of claim 11, wherein:communicate, via the at least one transceiver, over the first pathcomprises employing the first sequence number for the communication overthe first path from a time the first path is established until a timewhen the first path is terminated; and communicate, via the at least onetransceiver, over the second path comprises employing the secondsequence number for the communication over the second path from a timethe second path is established until a time when the second path isterminated.
 18. The mobile device of claim 11, wherein the at least oneprocessor is further configured to: employ the first sequence number forfurther communication of the mobile device with the first access pointthrough the first path; and employ the second sequence number forfurther communication of the mobile device with the second access pointthrough the second path, the first sequence number and the secondsequence number for ordering messages sent on the first path and thesecond path.
 19. The mobile device of claim 11, wherein the at least oneprocessor is further configured to: establish a third path between themobile device and a third access point; and communicate, via the atleast one transceiver, over the third path, wherein communication overthe third path is associated with a third sequence number, and whereinthe third sequence number is different from the first sequence numberand the second sequence number.
 20. The mobile device of claim 19,wherein the at least one processor is further configured to: perform ahandover from the first path or the second path to the third path.
 21. Amobile device, comprising: means for communicating over a first pathbetween the mobile device and a first access point, whereincommunication over the first path is associated with a first sequencenumber; and means for communicating over a second path between themobile device and a second access point, wherein communication over thesecond path is associated with a second sequence number, wherein thesecond sequence number is different from the first sequence number, andwherein the mobile device communicates over the first path and thesecond path simultaneously.
 22. The mobile device of claim 21, wherein:the means for communicating over the first path comprises means forcommunicating one or more first packets over the first path according toa messaging protocol, and the means for communicating over the secondpath comprises means for communicating one or more second packets overthe second path according to the messaging protocol.
 23. The mobiledevice of claim 22, wherein: the first sequence number is employed aspart of the messaging protocol for the one or more first packetscommunicated over the first path, and the second sequence number isemployed as part of the messaging protocol for the one or more secondpackets communicated over the second path.
 24. The mobile device ofclaim 21, wherein: the first sequence number is generated when themobile device registers with the first access point associated with thefirst path, and the second sequence number is generated when the mobiledevice registers with the second access point associated with the secondpath.
 25. The mobile device of claim 21, wherein: the first sequencenumber is associated with the first access point, and the secondsequence number is associated with the second access point.
 26. Themobile device of claim 21, wherein: the means for communicating over thefirst path comprises means for employing the first sequence number forthe communication over the first path from a time the first path isestablished until a time when the first path is terminated; and themeans for communicating over the second path comprises means foremploying the second sequence number for the communication over thesecond path from a time the second path is established until a time whenthe second path is terminated.
 27. The mobile device of claim 21,further comprising: means for employing the first sequence number forfurther communication of the mobile device with the first access pointthrough the first path; and means for employing the second sequencenumber for further communication of the mobile device with the secondaccess point through the second path, the first sequence number and thesecond sequence number for ordering messages sent on the first path andthe second path.
 28. The mobile device of claim 21, further comprising:means for establishing a third path between the mobile device and athird access point; and means for communicating over the third path,wherein communication over the third path is associated with a thirdsequence number, and wherein the third sequence number is different fromthe first sequence number and the second sequence number.
 29. The mobiledevice of claim 24, further comprising: means for performing a handoverfrom the first path or the second path to the third path.
 30. Anon-transitory computer-readable medium storing computer-executableinstructions, the computer-executable instructions comprising: at leastone instruction instructing a mobile device to communicate over a firstpath between the mobile device and a first access point, whereincommunication over the first path is associated with a first sequencenumber; and at least one instruction instructing the mobile device tocommunicate over a second path between the mobile device and a secondaccess point, wherein communication over the second path is associatedwith a second sequence number, wherein the second sequence number isdifferent from the first sequence number, and wherein the mobile devicecommunicates over the first path and the second path simultaneously.